CU*BASE GOLD requires that the following networks be routed to the CU*Answers CU*NextNET connection: For all CU*Answers privately routed networks below, all ports/services should be allowed outbound from the LAN Required for standard Production connectivity: 63.236.240.16/28 63.236.240.48/28 63.236.240.79/32 63.236.240.128/29 63.236.240.138/32 63.236.240.144/28 Required for HA/Disaster Recovery connectivity: 216.111.149.8/30 216.111.149.16/28 216.111.149.240/28 66.115.246.224/27 In addition to t  More...

If you are considering purchasing a new workstation, here are some questions to ask yourself to ensure that you get all the features you need! First, be sure to review the CU*BASE workstation hardware and software requirements on our best practices page: http://cuanswers.com/client_pm_bp_network.php When purchasing any workstation, consider: 32 or 64-bit Operating System? CU*BASE and ProDOC are compatible with either operating system - but CU*Answers cannot make any guarantees about third part  More...

Beginning with the 17.10 CUBASE Release (October 22, 2017 for online clients), CU*Answers implemented the CUFMAINT table, which includes data from the CUFMNT table, as well as additional data not included in CUFMNT. CU*Answers recommends using the CUFMAINT table for all report building and query activity. If you currently have any Queries using the CUFMNT table, they will still work, as CUFMNT is now a View over the C UFMAINT table but without all of the additional information, so it will s  More...

The following Reason Codes are used with the A2A processing: 00 - Payment accepted 01 - Invalid bank routing number 02 - Invalid checking account number 07 - Algorithm code invalid 08 - Invalid alternate company 09 - Missing or incomplete data in URL 10 - Invalid date format 11 - Invalid access number 16 - Bad password 17 - Invalid User ID 18 - Transaction already processed 19 - Account info does not match 20 - Invalid credit card number 21 - invalid credit card expiration date 22 - Credit card   More...

YTD Fees for loans on a statement come from file LNFEES. That file is updated as part of EOD for the sole purpose of printing of YTD and Period Fees totals on statements as per Reg Z. The LNFEES file has a bucket for each month for totaling all fees; it also has a YTD Fees bucket. For credit cards, Reg. Z fees are split out on the statement at the time the statement is created. Fee transactions are identified based on the criteria outlined below, and the YTD Fees and YTD Interest totals are c  More...

The following document types include masking of account numbers: Statements (regularly, mortgage, and credit card) - may vary by print vendor Receipts - done at the thermal printer Printed Notices - effective with the 18.07 release eNotices - when viewed by the member via online banking Misc. Mbr Account Forms - effective with the 17.05 release

Normal 0 false false false MicrosoftInternetExplorer4 /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:"Times New Roman"; mso-ansi-language:#0400; mso-fareast-language:#0400; mso-bidi-language:#0400;} First try: Checking the p  More...

With the 17.10 Release we implemented changes to this process to not allow posting to accounts restricted by Account Security. Previously, Direct/Mail Post (Tool #341) did not have controls to prevent users from posting to accounts that are restricted, either because of an employee type code or special security restrictions. (Employees could not view these accounts, but still had the ability to post to them.) With this release we have added an additional layer of security that will disallow po  More...

There is not a way to deny individual employee access to CU*Spy. Employee Security can be used to control access to Tool #329 CU*Spy Daily Reports , but this does not control other access points such as via the Timeout window or from within Inquiry and Phone Operator, as well as dozens of other places where documents can be scanned and retrieved. A little background on why Tool #329 can be controlled: When 17.03 release first went live, this tool, along with about a dozen others, were set up n  More...

Remote access listings can been seen through a canned query through OPER for self processors. This information is located in the booklet Auditing Employee Access to CU*BASE Tools. HICH D ATA C ENTER E MPLOYEES S IGNED O N TO Y OUR I S ERIES (S ELF P ROCESSORS O NLY ) RMTACCESS in your CUBASEFILE library. To review this database, use the following canned Query (or create your own using this file): On the initial screen you can enter selection criteria (such as the date). Refer to online help  More...

Please make sure the Flat screen has an Analog (VGA) connection. No upgrade is needed. check 21

Per the announcement from March 17, 2004, titled "Changes to the CU*BASE Standard and Short-Form Loan Applications," there is a new "Applicant is applying for joint credit" checkbox and line for initials on the last page of the standard long form and at the top of the standard short form. In both cases, both the member and the co-borrower are required to initial the form if applying for joint credit.